Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2.0.1) for Linux x86 Part Number B16228-03 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# What's New

This chapter describes new features in the Enterprise Manager 10g Release 2 (10.2.0.2) installer.

The new Enterprise Manager installer provides an installation that is almost completely automated. In this release, the Enterprise Manager installer also provides the following:

- Renders seamless multiple-Oracle home installations and configurations during a single session.

- Facilitates individual maintenance cycles for each of the top-level product components.

  This is brought about by installing the database and the Oracle Management Server (OMS) in separate Oracle homes. In this release, the Enterprise Manager installer will perform a chain install, wherein it will install the OMS, database, and the agent in separate Oracle homes (`oms10g`, `db10g`, and `agent10g`).

- Facilitates a Grid Control upgrade from 10.1.x release patchsets to 10.2.0.2

- Facilitates mass deployment of the Management Agent using the Agent Deploy application.

- Provides an out-of-box secure Enterprise Manager Grid Control environment.

- Provides automated startup scripts that help start the database, Management Service, listener, and the Management Agent during a machine reboot.

- Allows the user to resume the installation process from the point where it was aborted, through the built-in resumability feature of the installer.

## Multiple Oracle Home Installations

The Enterprise Manager installer provides for a seamless installation experience by performing multiple Oracle home installations, depending on the type of installation that is selected.

A typical Oracle Enterprise Manager installation will create a separate Oracle home for:

- Oracle Management Service

- Oracle Database

- Oracle Management Agent

Note: The Oracle homes that are created as sub-directories by the installer will be placed under the Parent Directory that you specify. The Oracle homes will be created as `db10g`, `oms10g`, and `agent10g`.

### Seamless Oracle Home Configurations

The Enterprise Manager installer performs seamless multiple Oracle home configurations during the installation process. The configuration tools that are run during installation will depend on the installation type that you have selected.

The following table lists all the configuration tools that are run during a typical Enterprise Manager installation (Install Enterprise Manager Using a New Database):

Product | Configuration Tools
--- | ---
Oracle Enterprise Manager Repository Database | Oracle Net Configuration Assistant Oracle Database Configuration Assistant
Oracle Enterprise Manager Grid Console | OC4j Configuration Assistant HTTP Server Configuration Assistant Java Configuration Assistant Web Cache Configuration Assistant Oracle iAS Instance Configuration Assistant Register DCM Plug-Ins with Enterprise Manager DCM Repository backups Assistant Enterprise Manager Technology Stack Upgrade Oracle Management Service Configuration
Oracle Management Agent | Agent Configuration Assistant

Note: Depending on the Install Type you have chosen, any or all of the configuration tools listed in the table above will be run.

### Running Root.sh (Linux/Solaris only)

You are now required to run only one script `allroot.sh,` in this release of the installer, as compared to the three `root.sh` scripts (one for each Oracle home) that you had to run in the previous release.

Note: If Enterprise Manager is the first Oracle product that you are installing, you will also be prompted to execute `orainstRoot.sh` along with `allroot.sh`.

## Resuming an Enterprise Manager Grid Control Installation

In the event of an unexpected termination of the installation process, the Resumability feature of the Installer allows you to resume the installation process (the next time the Installer is invoked) from the point where the installation was aborted.

## Out-of-Box Secure Grid Environment

The new Enterprise Manager 10g R2 installer provides a secure Grid Control environment out-of-box.

## Automated Startup Scripts

In this release of Enterprise Manager, the startup scripts to run the database, Management Service, listener, and agent are automatically executed in case a machine reboots. The services that are automatically started depend on the installation type that you have chosen.

Installing | Automated Scripts Start the
--- | ---
Enterprise Manager Using New Database | Repository database, listener, Management Service, and the agent.
Enterprise Manager Using Existing Database | Management Service and agent.
Additional Management Service | Management Service and agent.
Additional Management Agent | Agent only.

## Enhanced Installer Screens

The Enterprise Manager 10g R2 Installer's enhanced GUI provides for a more user-friendly installation experience.

### Installation Location

After you select the appropriate installation option in the first screen (Specify Installation Type), you will be prompted to specify the Parent Directory in the Specify Installation Location screen, wherein the Oracle homes are created automatically.

### Specify Configuration

The Specify Configuration screen for installing Enterprise Manager using an existing database has changed. The single Connect String value (comprising of host name, port, and SID) that you had to specify in the previous release has been changed to three input fields.

### Language Selection

This page has been removed. You can now select the required languages by clicking Product Languages in the Installation Location screen.

### Prefill Tablespace Location

The Specify Repository Database Configuration screen now includes the Prefill Tablespace Locations button. On clicking this button, the installer queries the database that you have specified, looks for the `SYSAUX` tablespace location, and automatically prefills that path in the appropriate tablespace location text boxes.

Note: If the tablespaces are stored in a raw device/ASM disk, then you must ensure the raw device/ASM disk is accessible to store the SYSMAN tablespaces.